Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-52297 | O112-C2-015700 | SV-66513r1_rule | Medium |
Description |
---|
Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised due to weak algorithms. Applications utilizing encryption are required to use approved encryption modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. FIPS 140-2 is the current standard for validating cryptographic modules, and NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified hardware-based encryption modules. Authentication modules with weak encryption could allow an attacker to gain access to data stored in the database and to the administration settings of the DBMS. |
STIG | Date |
---|---|
Oracle Database 11.2g Security Technical Implementation Guide | 2015-03-26 |
Check Text ( C-54353r1_chk ) |
---|
Review DBMS configuration to verify the DBMS is using NIST-validated FIPS 140-2-compliant cryptography for all authentication mechanisms. If NIST-validated FIPS 140-2-compliant cryptography is not being used for all authenticated mechanisms, this is a finding. - - - - - Check the Oracle SQLNET.ORA file for the following settings to see if Oracle Advanced Security option is installed. If Oracle Advanced Security Option is not installed, check with the DBA and SYSTEM Administrator to see if other mechanisms or third-party products are deployed to encrypt data during the transmission. The SQLNET.ORA is located in the $ORACLE_HOME/network/admin directory by default. Check the environment variable TNS_ADMIN to see exactly where the files are located. Use the following command to check the location in your environment. $ echo $TNS_ADMIN Oracle Advanced Security Network Encryption Settings #ASO Encryption sqlnet.encryption_server=accepted sqlnet.encryption_client=requested sqlnet.encryption_types_server=(AES_256) sqlnet.encryption_types_client=(AES_256) Oracle Advanced Security Network Data Integrity Settings #ASO Checksum sqlnet.crypto_checksum_server=requested sqlnet.crypto_checksum_client=requested sqlnet.crypto_checksum_types_server = (SHA1) sqlnet.crypto_checksum_types_client = (SHA1) |
Fix Text (F-57113r6_fix) |
---|
Utilize NIST-validated FIPS 140-2-compliant cryptography for all authentication mechanisms. The strength requirements are dependent upon data classification. For unclassified data, where cryptography is required: AES 128 for encryption SHA 256 for hashing NSA has established the suite B encryption requirements for protecting National Security Systems (NSS) as follows. AES 128 for Secret AES 256 for Top Secret SHA 256 for Secret SHA 384 for Top Secret National Security System is defined as: (OMB Circular A-130) Any telecommunications or information system operated by the United States Government, the function, operation, or use of which (1) involves intelligence activities; (2) involves cryptologic activities related to national security; (3) involves command and control of military forces; (4) involves equipment that is an integral part of a weapon or weapons system; or (5) is critical to the direct fulfillment of military or intelligence missions, but excluding any system that is to be used for routine administrative and business applications (including payroll, finance, logistics, and personnel management applications). There is more information on this topic in the Oracle Database 11.2g Advanced Security Administrator's Guide, which may be found at http://docs.oracle.com/cd/E11882_01/network.112/e40393.pdf FIPS 140-2 can be downloaded from http://csrc.nist.gov/publications/PubsFIPS.html#140-2 |